Hierarchical control system for optimal management of energy resources

ABSTRACT

Methods and systems are provided for optimizing energy management of an energy resource site. For instance, a hierarchical energy management system can provide optimized management of energy resource sites with large numbers of energy resources. In particular, the hierarchical energy management system can effectively control energy resources by allocating functionality using different tiers. For instance, one or more energy resources devices can comprise the lowest tier of the hierarchical energy management system. The next tier of the hierarchical energy management system can comprise one or more controllers that can manage the energy resource devices. The next tier of the hierarchical energy management system, a resource manager, generally manages the set of controllers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.63/148,912 filed Feb. 12, 2021, the entire contents of which is hereinincorporated by reference in its entirety.

BACKGROUND

Energy management systems are typically used to manage energy resources.For instance, energy management systems can be used to control variousenergy storage resources to meet the needs of an electrical grid and itsoperators. Managing electric energy storage can mitigate supply-demandimbalances, for example by storing electric energy during periods ofexcess supply and returning energy to an electric power grid duringperiods of excess demand. Accordingly, an energy management system canmanage the energy resources to meet the needs of an electrical grid andits operators.

SUMMARY

Embodiments of the present disclosure are directed towards hierarchicalenergy management system that can provide optimized management of energyresource sites with large numbers of energy resources. In accordancewith embodiments of the present disclosure, the system effectivelycontrols energy resources by allocating functionality using differenttiers. In particular, a resource manager is configured to manage a setof controllers, and each controller is configured to control variousenergy resource devices. Instead of allocating power over thestate-of-charge of individual energy storage devices, the resourcemanager can allocate power in accordance with an average of thestate-of-charge of the aggregations of energy storage devices associatedwith a corresponding controller. Such a hierarchical implementationenables efficient management of an extensive amount of energy resourcedevices.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

These and other features, aspects, and advantages of the presentdisclosure are better understood when the following Detailed Descriptionis read with reference to the accompanying drawings.

FIG. 1 depicts an example configuration of an operating environment inwhich some implementations of the present disclosure can be employed, inaccordance with various embodiments.

FIG. 2 depicts a further example configuration of an operatingenvironment in which some implementations of the present disclosure canbe employed, in accordance with various embodiments of the presentdisclosure.

FIG. 3 depicts an example configuration of an energy storage unit, inaccordance with various embodiments of the present disclosure.

FIG. 4 depicts a process flow showing an embodiment of a method foroptimized management of energy resource sites, in accordance withembodiments of the present disclosure.

FIG. 5 depicts a process flow showing a second embodiment of a methodfor optimized management of energy resource sites, in accordance withembodiments of the present disclosure.

FIG. 6 depicts a process flow showing a third embodiment of a method foroptimized management of energy resource sites, in accordance withembodiments of the present disclosure.

FIG. 7 is a block diagram of an example computing device in whichembodiments of the present disclosure may be employed.

DETAILED DESCRIPTION OF THE INVENTION

The subject matter of the present disclosure is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Oftentimes, energy management systems can be used to control variousenergy resources to meet the needs of an electrical grid and itsoperators. In this regard, energy storage systems are connected to anexternal electric power grid to provide the grid with energy storagecapabilities. In particular, electric energy storage can mitigatesupply-demand imbalances by storing electric energy during periods ofexcess supply and returning it to the electric power grid during periodsof excess demand. Electric energy storage can provide various benefitsfor utilities and other grid operators, including firming of wind andsolar power to address the intermittency of these power sources,improving reliability, outage backup, volt/VAR control, frequencyregulation and system upgrade deferral.

As the desire for using electric energy storage increases, energyresource sites are being deployed that are on an order of magnitudelarger than previous energy resource sites. For example, energy resourcesites are growing to accommodate an extensive number of energy storagedevices (e.g., batteries) for storing energy. As such, managing each ofthe energy storage devices is becoming increasingly time and resourceintensive. In particular, as conventional energy management systemstypically only control a relatively small number of energy resources, itis becoming more difficult to effectively manage the vast number ofenergy resources being deployed at an energy resource site.

Accordingly, embodiments of the present disclosure are directed to ahierarchical energy management system that allows for optimizedmanagement of energy resource sites with large numbers of energyresources. In particular, the hierarchical energy management system caneffectively control energy resources by allocating functionality usingdifferent tiers. For instance, one or more energy resources devices canbe managed via a hierarchical energy management implementation.

In operation, a resource manager can manage a set of controllers, whichin turn each control a set of energy resource devices. The resourcemanager can control allocation and apportionment of power for each ofthe energy resource devices in the system via the correspondingcontrollers. In particular, the resource manager can transmitinstructions to the set of controllers that indicate an allocation ofpower to apply to the aggregation of devices related to a particularcontroller (e.g., the aggregation of devices that a controllercontrols). Such an allocation and apportionment of power can bedesignated based on an average of the state of charge between anaggregations of devices (e.g., managed by a particular controller). Assuch, instead of working over the state-of-charge of individual energyresource devices to identify power allocation, the resource manager canwork over an average of the state-of-charge between the aggregations ofenergy resource devices (e.g., managed by the controllers).

In determining power allocation, the resource manager can do so inassociation with an operating mode(s), such as an operating modeselected by a user. Advantageously, the power allocation may bedetermined in light of a segmented implementation of modes (e.g.,application of an operating mode to a portion of the system instead ofto the entire system). For example, one set of operating modes can beused for a defined percentage of the system, and another set ofoperating modes can be used on another defined percentage of the system.This segmentation of operating modes can be based on a predeterminedconfiguration of energy resource devices at an energy resource site. Forexample, segmentation can be based on the physical layout of the site.As another example, segmentation can be based on a virtual division ofthe site.

The controllers, in communication with the resource manager, areconfigured to manage a corresponding set of energy resources devices. Inembodiments, the controllers may analyze constraints (e.g., a level ofpower that cannot be exceeded) and use such constraints to manage theenergy resource devices. Such constraints can be based on energyresource device limitations.

In controlling various energy resource devices, a controller may managethe charging and/or discharging of the energy resource devices such thatthe energy resource devices operate in accordance with a powerallocation determined by the resource manager. As such, each controlleris executed to manage a particular portion of energy resource devices atan energy resource site, as opposed to a single controller managing allthe energy resource devices at the site. In this way, the hierarchicalenergy management system increases scalability of energy resources thatcan be optimally managed at a site (e.g., by allowing any number ofenergy resource devices to be deployed at a site).

Turning to FIG. 1, FIG. 1 depicts an example configuration of anoperating environment in which some implementations can be employed, inaccordance with various embodiments of the present disclosure. It shouldbe understood that this and other arrangements described herein are setforth only as examples. Other arrangements and elements (e.g., machines,interfaces, functions, orders, and groupings of functions, etc.) can beused in addition to or instead of those shown, and some elements may beomitted altogether for the sake of clarity. Further, many of theelements described herein are functional entities that may beimplemented as discrete or distributed components or in conjunction withother components, and in any suitable combination and location. Variousfunctions described herein as being performed by one or more entitiesmay be carried out by hardware, firmware, and/or software. For instance,some functions may be carried out by a processor executing instructionsstored in memory as further described with reference to FIG. 7.

It should be understood that operating environment 100 shown in FIG. 1is an example of one suitable operating environment. Among othercomponents not shown, operating environment 100 includes a resourcemanager 102, a set of controllers 104 (e.g., controllers 104A and 104Bthrough 104N), and a set of energy resource devices 104 (e.g., energyresource devices 106A and 106B through 106N). Such components shown inFIG. 1 may be implemented via any type of computing device, such as oneor more of computing device 700 described in connection to FIG. 7, forexample. It should be understood that any number of devices, servers,and other components may be employed within operating environment 100within the scope of the present disclosure. Each may comprise a singledevice or multiple devices cooperating in a distributed environment.

Generally, the hierarchical energy management system 100 is generallyconfigured to manage energy resource devices in a hierarchical manner.In this regard, the hierarchical energy management system 100 candistribute operations being executed to effectively and efficientlymanage or control numerous energy resource devices operating at a siteor multiple sites. In particular, the hierarchical energy managementsystem 100 can implement a resource manager 102 to manage a set ofcontrollers 104, including controller 104A and 104B through 104N. Inturn, a single controller, such as controller 104A, can then be used tomanage an aggregation of energy resource devices 106. As can beappreciated, the resource manager 102 effectively manages or controlsvarious energy resource devices (e.g., energy resource devices106A-106N) via multiple controllers (e.g., 104A-104N).

As a non-limiting example, the resource manager 102 can be used tocontrol 150 different energy resource devices. These 150 energy resourcedevices can be divided into groups that can be managed as a conglomerateby a particular controller. For example, the 150 energy resource devicescan be divided into 10 groups, such that 10 different controllers eachmanage 15 energy resource devices. For instance, a controller canexecute instructions (e.g., based on an allocation and/or schedulingcommand received from the resource manager) such that the 15 energyresource devices it controls follow functionality as indicated by theresource manager. In this way, the resource manager can communicate withthe 10 controllers, with each of the 10 controllers in turncommunicating with the corresponding 15 energy resource devices. Such ahierarchical implementation enables efficient control of an extensivenumber of energy resource devices.

As described, the resource manager 102 generally manages energy resourcedevices via various controllers, such as a set of controllers 104A-104N.For instance, the resource manager 102 can be used to control allocationof power, or energy, in association with a set of controllers thatcontrol an aggregation of energy resource devices. In particular, theresource manager 102 can transmit instructions to controllers 104 thatindicate an allocation of power to apply to the aggregation of energyresource devices related to the corresponding controllers. Such anallocation of power can be determined by the resource manager 102 basedon an average of the state-of-charge between an aggregation of energyresource devices (e.g., managed by a particular controller).

Each controller 104 generally communicates with the resource manager 102and a set of energy resource devices, at least some of which thecontroller 104 controls. For example, controller 104A communicates withresource manager 102 and energy resource device 106A, 106B, 106C, and106D. At a high level, each controller 104 may communicate with thecorresponding set of energy resource devices to enable selection,installation, removal, exchange, maintenance, monitoring, control,charging, or discharging associated with energy resource devices (e.g.,energy storage devices and/or power conversion devices). In this regard,a controller 104 may enable performance optimization by controlling ortriggering differential charging or discharging of individual energyresource devices. For example, a controller may trigger charging ordischarging of energy storage devices during times of excess powergeneration, peak demand, load-following, smoothing intermittentgeneration, supplying ancillary services (e.g., frequency regulation),supplying power in an event of an outage, etc. As described herein, thecontroller may generate and/or provide a command to an appropriateenergy resource device (e.g., energy storage device and/or powerconversion device) to flow current at a given level to and/or from anexternal electric power grid.

To enable performance optimization, the controller 104 can monitorvarious metrics of interest associated with energy resource devices(e.g., energy storage devices and/or power conversion devices) therebyenabling differential charging or discharging of individual energystorage devices to optimize overall performance. For example, acontroller may monitor energy resource devices (e.g., energy storagedevices and/or power conversion devices) to monitor state-of-charge(SOC), cycle life, calendar life, voltage (e.g., maximum voltage,minimum voltage), current (e.g., maximum current, minimum current),power, charge profile, discharge profile, maximum charge rate, maximumdischarge rate, total energy capacity, and/or temperature to optimizeoverall performance by controlling differential charging or dischargingof individual devices. To this end, the controller 104 may collect datavia the various energy resource devices, or components associatedtherewith (e.g., voltage and current sensors), on the performance andoperation of the various energy resources devices. Such data may beanalyzed by the controller 104 and/or communicated to the resourcemanager 102 for analysis of the data. The controller 104 and/or resourcemanager 102 can utilize the collected data to optimize performance basedat least in part on a power or energy supply or demand (e.g., of anexternal system).

The energy resource devices 106 generally operate to facilitateutilization of an energy resource. In this regard, an energy resourcedevice, as used herein, generally refers to a device associated with anenergy resource (e.g., battery, solar, wind, etc.). In embodiments, suchenergy resources devices can be used to store and/or convert energy. Anenergy resource device can be any of a number of devices. By way ofexample, and not limitation, an energy resource device may be or includean energy storage device, a battery, a meter, a relay, a batterycontainer, a gas controller, an HVAC, a generator, a power conversiondevice (e.g., inverter or converter), any combination of these devices(e.g., an energy storage unit), or any other suitable device associatedwith energy resources. Energy resource devices with which a controllercommunicates may be devices associated with the electrical power grid(e.g., meters, relays, etc.).

In some cases, an energy resource device can include an energy storagedevice(s) and a power conversion device(s). An energy resource deviceincluding an energy storage device and a power conversion device isgenerally referred to herein as an energy storage unit (ESU). An energystorage device generally stores energy. One example of an energy storagedevice is a battery, which may be constructed from a wide variety ofbattery cell types and chemistries, including lithium-ion,nickel-cadmium, nickel-metal-hydride, lead-acid, zinc-air, and othercurrently available and emerging technologies. Energy storage devicesmay be of one or more types and sizes, provided by one or moresuppliers, and may have different electrical and/or physicalcharacteristics (e.g., energy capacity, power capacity, currentcapacity, voltage, etc.). A power conversion device refers to a devicethat converts power (e.g., AC-DC or DC-AC). Generally, power conversiondevices are configured to convert an electrical parameter of powertransferred to and from the energy storage devices. For instance, apower conversion device can convert a battery's DC output to AC for thegrid. By way of example, a power conversion device may convert AC powerto DC power to charge energy storage devices from an external source,such as an electric power grid, and/or convert DC power to AC power todischarge energy storage units to an external source, such as anelectric power grid. A power conversion device may be or include aninverter or a converter. Power conversion devices may be of one or moretypes and sizes, provided by one or more suppliers, and may havedifferent electrical and/or physical characteristics.

One example of an ESU is illustrated in FIG. 3. As shown in FIG. 3, anenergy storage unit (ESU) 300 includes a battery 302, a power conversiondevice 304, and software 306. The software 306 can be used to manage andcontrol the battery 302 and the power conversion device 304. As shown,the ESU 302 communicates with the electric power grid.

In embodiments, an energy resource device may include software tocontrol the device. In this regard, the energy resource devices caninclude one or more processors, and one or more computer-readable media.The computer-readable media may include computer-readable instructionsexecutable by the one or more processors. The instructions may beembodied by one or more applications. In the case an energy resourcedevice includes an energy storage device (e.g., battery) and a powerconversion device, both the energy storage device and the powerconversion device may include its own embedded software. Variousinterfaces may be used to communicate between devices, such as devicesbuilt by different companies. As such, a controller may communicate withenergy storage devices (e.g., batteries) and power conversion devicesprovided by different vendors.

As illustrated, the hierarchical energy management system 100 is coupledto an electric power grid 108. For example, the hierarchical energymanagement system 100 may connect to a power grid via an energy resourcedevice, such as a power conversion device. The hierarchical energymanagement system 100 may connect to a power distribution grid 108 toprovide the grid with energy storage capabilities. In particular, energystorage (e.g., electric energy storage) offers benefits to an electricpower grid, that is, for utilities and other grid operators to addressthe intermittency of various power sources (e.g., wind and solar power).Energy storage can also improve reliability, outage backup, volt/VARcontrol, frequency regulation and system upgrade deferral, among otherthings. The electric power grid 108 generally delivers or distributeselectricity. That is, an electrical grid includes an interconnectednetwork for delivering electricity from producers to consumers. Inembodiments, electric power grid 108 is operated by an electric utility.

In some embodiments, the hierarchical energy management system 100facilitates energy management associated with energy resource devices ata particular or single site (e.g., a particular location in connectionwith an electrical power grid). In other embodiments, the hierarchicalenergy management system 100 can facilitate energy management associatedwith multiple energy resource sites, each site having a set of energyresource devices 106. In this regard, the sites are positioned atdifferent locations along an electrical power grid.

As such, it should be appreciated that hierarchical energy managementsystem 100 may be provided via multiple devices arranged in adistributed environment that collectively provide the functionalitydescribed herein. Additionally, other components not shown may also beincluded within the distributed environment.

Referring to FIG. 2, aspects of an illustrative energy managementenvironment are shown, in accordance with various embodiments of thepresent disclosure. As shown in FIG. 2, an energy management environmentincludes a hierarchical energy management system 200, an electric powergrid 208, user device 210, and a data store 212.

In embodiments, the hierarchical management system 200, the electricpower grid 208, user device 210, and data store 212 may communicate vianetwork 214, which may be wired, wireless, or both. A network caninclude multiple networks, or a network of networks, but is shown insimple form so as not to obscure aspects of the present disclosure. Byway of example, a network can include one or more wide area networks(WANs), one or more local area networks (LANs), one or more publicnetworks such as the Internet, and/or one or more private networks.Where a network includes a wireless telecommunications network,components such as a base station, a communications tower, or evenaccess points (as well as other components) may provide wirelessconnectivity. Networking environments are commonplace in offices,enterprise-wide computer networks, intranets, and the Internet. Thenetwork may be any network that enables communication among machines,databases, and devices (mobile or otherwise). Accordingly, the networkmay be a wired network, a wireless network (e.g., a mobile or cellularnetwork), a storage area network (SAN), or any suitable combinationthereof. In an example embodiment, the network includes one or moreportions of a private network, a public network (e.g., the Internet), orcombination thereof.

The hierarchical energy management system 200 can work in conjunctionwith any number of data stores 212. For example, each component ordevice may include or have access to a data store. A data store 212 canstore computer instructions (e.g., software program instructions,routines, or services), data, and/or models used in embodimentsdescribed herein. In some implementations, data store 212 can storeinformation or data received via the various components or devices ofhierarchical energy management system 200 and provides the variousdevices and/or components with access to that information or data, asneeded. Further, the information in data store 212 may be distributed inany suitable manner across one or more data stores for storage (whichmay be hosted externally). In embodiments, data store 212 can be used tostore information related to energy management. As one example, suchinformation can include information indicative of a system goal for anenergy resource site comprising energy resources. As another example,such information stored in a data store 212 may include data collectedfrom energy resource devices, such as, for example, state-of-charge(SOC), cycle life, calendar life, voltage (e.g., maximum voltage,minimum voltage), current (e.g., maximum current, minimum current),power, charge profile, discharge profile, maximum charge rate, maximumdischarge rate, total energy capacity, temperature, etc. As yet otherexamples, data store 212 may store operating modes, constraints,schedules, and/or the like.

The user device 210 may include an application utilized by a user tointerface with the functionality implemented via a hierarchical energymanagement system 200. An application(s) included on user device 210 maygenerally be any application capable of facilitating the exchange ofinformation between the user device and the hierarchical energymanagement system 200 in carrying out energy management related toenergy resource devices. In some implementations, the application(s)comprises a web application, which can run in a web browser, and couldbe hosted at least partially on a server. In addition, or instead, theapplication(s) can comprise a dedicated application, such as anapplication having energy management functionality. In some cases, theapplication is integrated into the operating system (e.g., as aservice).

In particular, the user device 210 can be used (e.g., by a user) toinput or identify goals (e.g., via operating modes) related to energymanagement associated with a set of energy resources, or devicesassociated therewith. For example, a user can input one or moreoperating modes that relate to a system goal for a site. In addition, insome embodiments, a user may input or identify constraints related toone or more energy resource devices. For instance, constraints can bebased on a defined power limit due to device limitations. Otherinformation can also be input via the user device, such as, for example,a predetermined configuration of energy resource devices at the energyresource site. For instance, in some embodiments, a predeterminedconfiguration of which energy resource devices correspond with whichcontrollers can be based on a physical layout of the energy resourcesite. In other embodiments, a predetermined configuration of whichenergy resource devices correspond with which controllers can be basedon a virtual division of the energy resource site related to a definedpercentage of the set of energy resource. In addition to inputtinginformation via the user device 210, the user device 210 can alsopresent information or data related to energy management.

As depicted, hierarchical energy management system 200 includes energyresource manager 202, controllers 204A-204N, and energy resource devices206A-206N. Any number of devices or components may be used to implementfunctionality described herein. Although the energy resource devices 206are generally illustrated in connection with the hierarchical energymanagement system 200, energy resource devices 206 may additionally oralternatively corresponding with a grid, such as an electrical powergrid. For example, various energy resource devices with which thecontrollers 204 communicate may be meters or relays of the electricalpower grid.

Hierarchical energy management system 200 can generally be used foroptimized management of energy resource devices, such as energy storagedevices and power conversion devices. Specifically, the hierarchicalenergy management system can be configured to allocate functionality bycontrolling energy resources using different tiers of control ormanagement. In particular, the hierarchical energy management system 200can implement a resource manager to manage a set of controllers. Inturn, each controller of the set of controllers can then be used tomanage an aggregation of energy resource devices (e.g., energy storageunits).

Resource manager 202 can be used to manage a set of controllers, such ascontroller 204A through 204N to effectuate control of energy resourcedevices. In this regard, resource manager 202 communicates with a set ofcontrollers, which each in turn communicate with an aggregation ofenergy resource devices. To manage a set of controllers, the resourcemanager 202 may include a power engine 220, an allocation engine 222,and a scheduler engine 224.

The power engine 220 is generally configured to identify an amount ofpower associated with a system. In this regard, the power engine 220 canidentify an amount of power for applying or using within a system (i.e.the set of resource energy devices managed by the resource manager 202).In some cases, to identify an amount of power for the system, anoperating mode(s) is used. An operating mode generally indicates a modeof operation to implement in association with a particular achievement,objective, or goal. In this way, an operating mode facilitatesidentification of a power amount using an algorithm(s) correspondingwith an operating mode to attain a particular outcome. As an example, ata high level, an operating mode can indicate a system goal such thatpower is maintained at a particular level (e.g., based on maintainingpower at a particular point and/or meter). Each operating mode may haveits own corresponding goal so that when the mode is enabled, theoperating mode helps to meet the system goal.

Examples of operating modes include peak power limiting mode, forecastassurance mode, volt/watt mode, power smoothing mode, limited wattsmode, power following mode, power factor correction mode, frequencycorrection mode, state-of-charge maintenance mode, spinning reservesmode, or the like. Peak power limiting mode generally responds to realpower levels on the grid, driving the charging or discharging of anESU(s) to transcend system bottlenecks and meet peaks in demand.Forecast assurance mode generally responds to a forecast of power useand real power levels on the grid, driving charging or discharging of anESU(s) to avoid high-cost energy purchases. Volt/Watt mode generallyresponds to voltage levels on the grid, driving the charging ordischarging of an ESU(s) to maintain voltage within the specified band.Power smoothing mode generally responds to real power levels on thegrid, driving the charging or discharging of an ESU(s) to maintainvoltage within the specified brand. Limited watts mode generally capsthe real power output of an ESU(s). Power following mode generallydrives the real power output of an ESU(s) in response to demand on asub-circuit. Power factor correction mode generally drives reactivepower output of an ESU(s) in response to power factor readings anywhereon the grid. Frequency correction mode generally maintains frequencywithin limits by charging or discharging an ESU(s). State-of-chargemaintenance mode generally restores a battery(s) in an ESU(S) to atarget state of charge. Spinning reserves mode generally appliesfrequency correction as a first priority and state-of-charge maintenanceas a second priority.

In some embodiments, such operating modes can be implemented such thatthere is segmentation of operating modes associated with differentportions of a system (e.g., energy resource devices associated with theresource manager). In this way, the resource manager 202 can controldifferent energy resource devices at a site based on the differentoperating modes. For example, the power engine can identify power inassociation with a portion of energy resource devices using a first setof operating modes, and power in association with a second portion ofenergy resource devices using a second set of operating modes. In somecases, the power engine 220 can implement segmentation based on apredetermined configuration of energy resource devices and/orcontrollers at a site. For example, segmentation can be based on thephysical layout of the site. In other cases, segmentation can be basedon a virtual division of the site (e.g., allocations based onpercentages of the devices in the system).

As can be appreciated, any number of operating modes can be applied andused to identify an extent of power in association with the system. Suchoperating modes can be selected or input by a user of user device 210.For example, a user may specify a particular operating mode to useduring various time durations. In other cases, operating modes may beautomatically identified based on information identified in associationwith energy resource devices, the electric grid, and/or the like.

As such, generally, the resource manager 202 identifies an operatingmode(s) and uses the operating mode, or algorithms associated therewith,to identify an amount of power in association with the system. In somecases, the operating mode(s) and/or power amount is used by the resourcemanager 202 to determine power allocation, as described more fullybelow. Additionally or alternatively, in some cases, the operatingmode(s) and/or power amount can be communicated to the controllers 204.

The allocation engine 222 is generally configured to determineallocation of power in association with energy resource devices. Inparticular, the allocation engine 222 can use the power identified viathe power engine 220 and determine an allocation of the power to applyin association with energy resource devices. As such, the allocationengine 222 can determine how much power to issue to various energyresource devices in connection with meeting a power objective or goal.In operation, the allocation engine 222 can analyze data and determinean allocation of power for energy resource devices. Such an allocationof power can be designated based on an average of the state-of-chargebetween aggregations of energy resource devices (e.g., managed by aparticular controller). As such, an average state-of-charge of energystorage devices or ESUs associated with each controller can bedetermined and used to allocate power to the energy storage devices orESUs associated with the corresponding controller.

By way of example only, assume an average state-of-charge is determinedfor a first set of energy resource devices 206A-206D, and an averagestate-of-charge is determined for a second set of energy resourcedevices 206E-206H. In some cases, such an average state-of-charge may bedetermined via the controllers 204A and 204N, respectively, based ondata collected in association with the corresponding energy resourcedevices. In other cases, the controllers 204A and 204N may collect datain association with the corresponding energy resource devices, andprovide such data to the resource manager 202 that may determine averagestate-of-charges (e.g., via the allocation engine 222). Based on thedetermined average state-of-charge associated with the first set ofenergy resource devices and the second set of energy resource devices,the allocation engine 222 may determine a power allocation for both thefirst set and the second set of energy resource devices.

In determining power allocation, the allocation engine 222 may analyzevarious constraints. A constraint generally refers to a limit orthreshold related to power or electricity. A constraint may be a generalsystem constraint or a constraint particular to a specific energyresource device or type of energy resource device. An initiallydetermined power allocation may be analyzed in accordance with arelevant constraint(s) to determine validity of the power allocation.For example, a constraint may indicate that a total power (e.g., inassociation with a particular energy resource device) cannot exceed athreshold power level. In this regard, the power allocation may beanalyzed in light of the threshold power level constraint. As anotherexample, a constraint may indicate a state-of-charge threshold or valuerange. As such, the power allocation may be analyzed in light of thestate-of-charge threshold or value ranges. In the event the powerallocation is invalid based on a constraint, the allocation engine 222may modify the power allocation within the confines of the constraint.

As can be appreciated, any number of constraints can be applied and usedto identify a power allocation, or validity thereof, in association withenergy resource devices. Such constraints can be selected or input by auser of user device 210. For example, a user may specify a particularconstraint to use during various time durations. In other cases,constraints may be automatically identified based on informationidentified in association with energy resource devices, the electricgrid, and/or the like.

As such, generally, the allocation engine 222 identifies powerallocation to apply in association with sets of energy resource devicescorresponding to particular controllers. The power allocation may bespecific to the controllers (or set of corresponding energy resourcedevices) and/or specific to the particular energy resource devices. Forexample, in some cases, the power allocation may be specific to a set ofenergy resource devices associated with a controller. In such cases, thecontroller may determine power allocation specific to the correspondingresource devices. In other cases, the power allocation determined at theresource manager may be specific to the energy resource devices.

In some cases, the power allocation is used by the scheduler engine 224to determine schedules, as described more fully below. Additionally oralternatively, in some cases, the power allocations can be communicatedto the controllers 204. In particular, in accordance with determining apower allocation, the resource manager 202 can transmit instructions tothe set of controllers that indicate an allocation of power to apply tothe aggregation of energy resource devices related to a particularcontroller(s) (e.g., the aggregation of energy resource devices that acontroller controls). In some cases, a same instruction may becommunicated to each of the controllers. For example, an allocationengine 222 may allocate a first amount of power for a first set ofenergy resource devices associated with a first controller and a secondamount of power for a second set of energy resource devices associatedwith a second controller. Both power allocations may be included in aninstruction communicated to both the first controller and the secondcontroller. In other cases, a first instruction may be communicated tothe first controller indicating the power allocation, and a secondinstruction different from the first instruction may be communicated tothe second controller indicating the power allocation associated withthe second set of energy resource devices.

The scheduler engine 224 is generally configured to determine a schedulefor performing various load operations in association with energyresource devices. For example, a schedule may include indications as towhen to charge and/or discharge an energy resource device(s). Asdescribed herein, the scheduler engine 224 can use the power allocationto identify an appropriate schedule for performing load operations. Inembodiments, the scheduler engine 224 may also use pricing, resourcelimits, maintenance events, among other things, to optimize a schedulefor performing load operations. The scheduler engine 224 can provide theschedule, or portion thereof, to the controllers 204 for implementingthe schedule of performing load operations.

Controllers 204 are generally configured to control a corresponding setof energy resource devices, or portion thereof. In this regard,controllers 204 can control charging and/or discharging of variousenergy resource devices. To do so, each controller 204 communicates witha corresponding set of energy resource devices and resource manager 202.The controller 204 may obtain operation instructions or commands fromthe resource manager 202. For instance, the resource manager 202 mayprovide a schedule indicating when to charge and/or discharge variousenergy resource devices and a corresponding amount. As another example,the resource manager 202 may provide an allocation of power for use by acorresponding set of energy resource devices. In some cases, theallocation of power may be specific to the particular energy resourcedevices. In other cases, the allocation of power may be designated forthe corresponding set of energy resource devices, and the controller 204determines the particular power to allocate for each particular energyresource device.

Each controller 204 may include various engines, such as a power engine,an allocation engine, and a scheduler engine, as described above inassociation with the resource manager 202. Such a power engine,allocation engine, and/or schedule engine in association with acontroller 204 can operate similarly as described above in relation tothe resource manager 202. However, such engines at a controller operatein association with the corresponding set of energy resource deviceswith which the controller communicates. By way of example, a poweramount, a power allocation, and/or power schedule may be determined bycontroller 204A in association with energy resource devices 206A-206D.As a specific example, a controller 204 may access a set of constraintsassociated with the corresponding set of energy resource devices, orportion thereof, and utilize the constraints to analyze power allocationand/or schedule. For example, constraints based on an energy resourcedevice limitation (e.g., level of power that cannot be exceeded) may beaccessed and analyzed to validate that the designated power associatedwith the particular device is not exceeded. Advantageously, if needed,the controller 204 may adjust or modify particular power operationsand/or schedules to adapt to the particular energy resource devicesbeing controlled by the particular controller.

As previously described, the controllers 204 can monitor data associatedwith the energy resource devices. In this way, the controllers canreceive data from energy resource devices 206 and analyze such dataand/or provide such data to the resource manager for analysis. As oneexample, the controllers 204 may use a control loop to measure outputassociated with energy resource devices (e.g., power of a meter andenergy storage device) and adjust to achieve the power target at themeter.

In some implementations, controllers 204 may be configured to facilitateislanding operations. Islanding operations refer to operations relatedto islanding, or isolating, a portion of an electric power grid,generally referred to herein as an islanded microgrid. Generally, anislanded microgrid refers to a sub-network of an electric power gridthat has been isolated from the main grid. In such cases, the controller204 may detect an event and, based on the event, initiate an islandingmode such that the corresponding energy resource devices (e.g., ESUs)communicate with the specific islanded microgrid. An event may be anyoccurrence or instance for which transitioning to a microgrid isdesirable. By way of example only, an event may be a power outage, lossof voltage on the grid (e.g., to a threshold amount), or the like. Inimplementations, in accordance with detecting an event, the controller,or other component, can form the islanded microgrid for utilization. Ascan be appreciated, conditions or events for triggering use of anislanded microgrid and/or conditions or configurations for forming anislanded microgrid are configurable (e.g., via a user of a user device).Enabling configuration of islanded microgrids and/or use thereof enablescustomization for a particular site, customer, etc.

Energy resource devices 206 can facilitate utilization of an energyresource. In this regard, the energy resource devices 206 can executeinstructions received from a controller to manage the energy resourcedevice, or portion thereof, such as storage or energy conversionassociated with an ESU. For example, energy resource devices, such asESUs can charge and/or discharge in accordance with power allocationand/or allocation scheduled received from a controller.

In some embodiments, the energy resource devices 206 can be used as partof a control loop to measure power. For instance, the energy resourcedevices 206 can be used to measure power at a device, a meter, and/or areference point. In some cases, such measured power can be used by theenergy resource device 206 to adjust power charge and/or discharge, forexample, to align with a designated power allocation (e.g., to maintaina predefined energy resource goal for an aggregation of devices).Additionally or alternatively, such measured power can then becommunicated, for instance, to the corresponding controllers. Inembodiments, the controller 204 can average the power levels across anaggregation of energy resources devices. The controller 204 and/orresource manager 202 can then use this aggregation to adjust theallocation and/or apportionment of power accordingly to maintain thegoal as indicated via an operating mode (e.g., a level of power thatcannot be exceeded). By way of example only, to execute a control loop,a controller can measure and/or receive a measurement of a level ofpower at an energy resource device, as well as a measurement of a levelof power at a reference point (e.g., meter). In some instances, thecontroller (e.g., controller 204A) can then adjust an overall level ofpower to the energy resource device (e.g., one of devices 206A-206D)based on these measurements of power. In other instances, the controller(e.g., controller 204A) can average measurements of power across theaggregation of devices (e.g., devices 206A-206D) and communicate thisaveraged state-of-charge to the resource manager 202, which can thenadjust an overall level of power to the aggregation of devices (e.g.,devices 206A-206D) based on the averaged state-of-charge.

As such, the energy resource devices 206 can communicate with thecorresponding controller 204, for example, to provide data to thecontroller for analysis (e.g., an energy analysis performed by thecontroller 204 and/or resource manager 202). The energy resource devices206 can also communicate with the electric power grid 208 to charge fromand/or discharge to the grid. In this regard, the energy resourcedevices 206 can accept current from or inject current into the electricpower grid 208. In this way, energy resource devices, such as ESUs mayact as an AC source or load for the electric power grid 208.

As described above, in some embodiments, the energy resource devices 206may charge from and/or discharge to an islanded microgrid, such as asub-network of electric power grid 208. Utilization of an islandedmicrogrid may occur in response to an indication that the sub-network isisolated from a main grid. Upon receiving an indication (e.g., from acontroller), the energy resource device may discharge to the islandedmicrogrid until its charging capability is depleted to a lowestacceptable level, or until another indication is received indicatingthat the affected microgrid is no longer isolated.

Turning now to FIGS. 4-6, FIGS. 4-6 provide exemplary methods forperforming various embodiments described herein. With initial referenceto FIG. 4, a process flow is provided showing an embodiment of method400 for optimized management of energy resource sites, in accordancewith embodiments of the present disclosure. Method 400 can be performed,for example by hierarchical energy management system 100 as illustratedin FIG. 1 and/or the hierarchical energy management system 200 asillustrated in FIG. 2.

Initially, at block 402, a power amount for a system is determined. Inembodiments, a power amount may be determined in accordance with anoperating mode(s) to be used by the system, or a portion thereof. Atblock, 404, a power allocation associated with a set of energy resourcedevices is determined. In embodiments, the power allocation isdetermined using metrics associated with various portions of the energyresource devices. For example, an average state-of-charge associatedwith a first set of energy resource devices and an averagestate-of-charge associated with a second set of energy resource devicescan be used to determine a power allocation for the first set of energyresource devices and for the second set of energy resource devices. Insome implementations, the power allocation may be used to generate aschedule used to perform load operations. At block 406, the powerallocation is communicated to each controller of a set of controllers.Thereafter, at block 408, a controller, of the set of controllers, canmanage load operations (e.g., charging and/or discharging) associatedwith a set of energy resource devices of which the controller manages.In this way, the controller can communicate with the corresponding setof energy resource devices to manage load operations and monitor dataobtained from the energy resource devices. As can be appreciated, insome implementations, the controller can analyze constraints, power,etc. to adjust, modify, or distribute power allocation related to theset of energy resources devices it is managing and/or schedulesassociated therewith.

With reference to FIG. 5, a process flow is provided showing anembodiment of method 500 for optimized management of energy resourcesites, in accordance with embodiments of the present disclosure. Method500 can be performed, for example by hierarchical energy managementsystem 100 as illustrated in FIG. 1 and/or the hierarchical energymanagement system 200 as illustrated in FIG. 2. In particular, aspectsof method 500 can be performed via a resource manager, such as resourcemanager 102 of FIG. 1 and/or resource manager 202 of FIG. 2.

Initially, at block 502, an amount of power for a set of energy storageunits is identified. Each energy storage unit can include an energystorage device and a power conversion device that interfaces with anelectric power grid. In embodiments, an amount of power can bedetermined based on an operating mode, for example, specified by a uservia a user device. At block 504, an allocation of power for a firstplurality of energy storage units associated with a first controller anda second plurality of energy storage units associated with a secondcontroller is determined. The allocation of power may be determinedbased on a first state-of-charge metric (e.g., average state-of-charge)associated with the first plurality of energy storage units and a secondstate-of-charge (e.g., average state-of-charge) associated with thesecond plurality of energy storage units. The allocation of power mayalso be determined based on a set of constraints, such as constraintsprovided by a user via a user device. The constraints may be used torefine or adjust an initially determined allocation of power. At block506, a schedule is determined in association with the allocation ofpower. Thereafter, at block 508, the allocation of power and/or scheduleis provided to the the first controller that controls the firstplurality of energy storage units and the second controller thatcontrols the second plurality of energy storage units.

With reference to FIG. 6, a process flow is provided showing anembodiment of method 600 for optimized management of energy resourcesites, in accordance with embodiments of the present disclosure. Method600 can be performed, for example by hierarchical energy managementsystem 100 as illustrated in FIG. 1 and/or the hierarchical energymanagement system 200 as illustrated in FIG. 2. In particular, aspectsof method 600 can be performed via a controller, such as controller 104Aof FIG. 1 and/or controller 204A of FIG. 2.

Initially, at block 602, an indication of a power allocation associatedwith a set of energy storage units is received from a resource manager.In embodiments, each energy storage unit includes an energy storagedevice and a power conversion device that interfaces with an electricpower grid. The power allocation may be determined based on an averagestate-of-charge associated with the set of energy storage units and anaverage state-of-charge associated with other sets of energy storageunits (e.g., that are managed by other controllers). Based on theindication of the power allocation associated with the set of energystorage units, at block 604, charging from and/or discharging to theelectric power grid is managed in association with each of the energystorage units of the set of energy storage units. At block 606, data isobtained from energy storage units. Thereafter, at block 608, the datais provided to the resource manager and/or analyzed to adjust powerallocation and/or charging/discharging of an energy storage unit(s).

Having described embodiments of the present invention, an exampleoperating environment in which embodiments of the present invention maybe implemented is described below in order to provide a general contextfor various aspects of the present invention. Referring to FIG. 7, anillustrative operating environment for implementing embodiments of thepresent invention is shown and designated generally as computing device700. Computing device 700 is but one example of a suitable computingenvironment and is not intended to suggest any limitation as to thescope of use or functionality of the invention. Neither should thecomputing device 800 be interpreted as having any dependency orrequirement relating to any one or combination of componentsillustrated.

Embodiments of the invention may be described in the general context ofcomputer code or machine-useable instructions, includingcomputer-executable instructions such as program modules, being executedby a computer or other machine, such as a smartphone or other handhelddevice. Generally, program modules, or engines, including routines,programs, objects, components, data structures, etc., refer to code thatperform particular tasks or implement particular abstract data types.Embodiments of the invention may be practiced in a variety of systemconfigurations, including hand-held devices, consumer electronics,general-purpose computers, more specialized computing devices, etc.Embodiments of the invention may also be practiced in distributedcomputing environments where tasks are performed by remote-processingdevices that are linked through a communications network.

With reference to FIG. 7, computing device 700 includes a bus 710 thatdirectly or indirectly couples the following devices: memory 712, one ormore processors 714, one or more presentation components 716,input/output ports 718, input/output components 720, and an illustrativepower supply 722. Bus 710 represents what may be one or more busses(such as an address bus, data bus, or combination thereof). Although thevarious blocks of FIG. 7 are shown with clearly delineated lines for thesake of clarity, in reality, such delineations are not so clear andthese lines may overlap. For example, one may consider a presentationcomponent such as a display device to be an I/O component, as well.Also, processors generally have memory in the form of cache. Werecognize that such is the nature of the art, and reiterate that thediagram of FIG. 7 is merely illustrative of an example computing devicethat can be used in connection with one or more embodiments of thepresent disclosure. Distinction is not made between such categories as“workstation,” “server,” “laptop,” “hand-held device,” etc., as all arecontemplated within the scope of FIG. 8 and reference to “computingdevice.”

Computing device 700 typically includes a variety of non-transitorycomputer-readable media. Non-transitory Computer-readable media can beany available media that can be accessed by computing device 700 andincludes both volatile and nonvolatile media, removable andnon-removable media. By way of example, and not limitation,non-transitory computer-readable media may comprise non-transitorycomputer storage media and communication media.

Non-transitory computer storage media include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer-readableinstructions, data structures, program modules or other data.Non-transitory computer storage media includes, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by computing device 700.Non-transitory computer storage media excludes signals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of any ofthe above should also be included within the scope of computer-readablemedia.

Memory 712 includes computer storage media in the form of volatileand/or nonvolatile memory. As depicted, memory 712 includes instructions724. Instructions 724, when executed by processor(s) 714 are configuredto cause the computing device to perform any of the operations describedherein, in reference to the above discussed figures, or to implement anyprogram modules described herein. The memory may be removable,non-removable, or a combination thereof. Illustrative hardware devicesinclude solid-state memory, hard drives, optical-disc drives, etc.Computing device 700 includes one or more processors that read data fromvarious entities such as memory 712 or I/O components 820. Presentationcomponent(s) 716 present data indications to a user or other device.Illustrative presentation components include a display device, speaker,printing component, vibrating component, etc.

I/O ports 718 allow computing device 700 to be logically coupled toother devices including I/O components 720, some of which may be builtin. Illustrative components include a microphone, joystick, game pad,satellite dish, scanner, printer, wireless device, etc.

Embodiments presented herein have been described in relation toparticular embodiments which are intended in all respects to beillustrative rather than restrictive. Alternative embodiments willbecome apparent to those of ordinary skill in the art to which thepresent disclosure pertains without departing from its scope.

From the foregoing, it will be seen that this disclosure in one welladapted to attain all the ends and objects hereinabove set forthtogether with other advantages which are obvious and which are inherentto the structure.

It will be understood that certain features and sub-combinations are ofutility and may be employed without reference to other features orsub-combinations. This is contemplated by and is within the scope of theclaims.

In the preceding detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown, by way ofillustration, embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.Therefore, the preceding detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Various aspects of the illustrative embodiments have been describedusing terms commonly employed by those skilled in the art to convey thesubstance of their work to others skilled in the art. However, it willbe apparent to those skilled in the art that alternate embodiments maybe practiced with only some of the described aspects. For purposes ofexplanation, specific numbers, materials, and configurations are setforth in order to provide a thorough understanding of the illustrativeembodiments. However, it will be apparent to one skilled in the art thatalternate embodiments may be practiced without the specific details. Inother instances, well-known features have been omitted or simplified inorder not to obscure the illustrative embodiments.

Various operations have been described as multiple discrete operations,in turn, in a manner that is most helpful in understanding theillustrative embodiments; however, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations need not be performed in theorder of presentation. Further, descriptions of operations as separateoperations should not be construed as requiring that the operations benecessarily performed independently and/or by separate entities.Descriptions of entities and/or modules as separate modules shouldlikewise not be construed as requiring that the modules be separateand/or perform separate operations. In various embodiments, illustratedand/or described operations, entities, data, and/or modules may bemerged, broken into further sub-parts, and/or omitted.

The phrase “in one embodiment” or “in an embodiment” is used repeatedly.The phrase generally does not refer to the same embodiment; however, itmay. The terms “comprising,” “having,” and “including” are synonymous,unless the context dictates otherwise. The phrase “A/B” means “A or B.”The phrase “A and/or B” means “(A), (B), or (A and B).” The phrase “atleast one of A, B and C” means “(A), (B), (C), (A and B), (A and C), (Band C) or (A, B and C).”

What is claimed is:
 1. A computer-implemented method, the methodcomprising: identifying an amount of power for a set of energy storageunits, each energy storage unit including an energy storage device and apower conversion device that interfaces with an electric power grid;determining an allocation of power for a first plurality of energystorage units associated with a first controller and a second pluralityof energy storage units associated with a second controller, theallocation of power determined based on a first state-of-charge metricassociated with the first plurality of energy storage units and a secondstate-of-charge associated with the second plurality of energy storageunits; and providing the allocation of power for the first plurality ofenergy storage units to the first controller that controls the firstplurality of energy storage units and the allocation of power for thesecond plurality of energy storage units to the second controller thatcontrols the second plurality of energy storage units.
 2. The method ofclaim 1, wherein the amount of power for the set of energy storage unitsis identified based on an operating mode implemented to obtain aparticular objective.
 3. The method of claim 1, wherein determining theallocation of power is based on one or more constraints associated withat least a portion of the set of energy storage units.
 4. The method ofclaim 1, wherein the first state-of-charge metric comprises an averagestate-of-charge of the first plurality of energy storage units, and thesecond state-of-charge comprises an average state-of-charge of thesecond plurality of energy storage units.
 5. The method of claim 1,further comprising: receiving, via the first controller and the secondcontroller, data associated with the first plurality of energy storageunits and the second plurality of energy storage units; and using thedata associated with the first plurality of energy storage units and thesecond plurality of energy storage units to adjust the allocation ofpower for the first plurality of energy storage units and the secondplurality of energy storage units.
 6. The method of claim 1, wherein thefirst plurality of energy storage units is controlled by the firstcontroller and the second plurality of energy storage units iscontrolled by the second controller based on a predeterminedconfiguration of the set of energy storage units at an energy resourcesite.
 7. The method of claim 1, further comprising determining aschedule for performing load operations in association with the set ofenergy storage units, wherein the allocation of power for the firstplurality of energy storage units and the second plurality of energystorage units is provided to the first controller and the secondcontroller in association with the schedule.
 8. The method of claim 7,wherein the load operations comprise charging and/or discharging inassociation with at least a portion of the set of energy storage units.9. One or more computer storage media storing computer-useableinstructions that, when used by one or more computing devices, cause theone or more computing devices to perform operations comprising:receiving, from a resource manager, an indication of a power allocationassociated with a first set of energy storage units, each energy storageunit including an energy storage device and a power conversion devicethat interfaces with an electric power grid, the power allocationdetermined based on an average state-of-charge associated with the firstset of energy storage units and an average state-of-charge associatedwith the second set of energy storage units; and based on the indicationof the power allocation associated with the first set of energy storageunits, managing charging from and/or discharging to the electric powergrid in association with each of the energy storage units of the firstset of energy storage units.
 10. The one or more computer storage mediaof claim 9, wherein managing charging from and/or discharging to theelectric power grid comprises analyzing constraints associated with atleast a portion of the first set of energy storage units.
 11. The one ormore computer storage media of claim 9, further comprising: obtainingdata associated with the first set of energy storage units; and usingthe data to adjust charging and/or discharging in association with atleast one of the energy storage units of the first set of energy storageunits.
 12. The one or more computer storage media of claim 9, furthercomprising: obtaining data associated with the first set of energystorage units, the data obtained from the first set of energy storageunits and one or more energy resource devices; and providing the data tothe resource manager for use in analyzing the power allocationassociated with the first set of energy storage units.
 13. The one ormore computer storage media of claim 9, further comprising adjusting thepower allocation associated with the first set of energy storage unitsby: identifying a first set of power levels at each energy storage unitof the first set of energy storage units; identifying a second set ofpower levels at one or more reference points; and adjusting the powerallocation based on a comparison of the first set of power levels ateach energy storage unit of the first set of energy storage units withthe second set of power levels at the one or more reference points. 14.The one or more computer storage media of claim 9, wherein theindication of the power allocation is received in association with aschedule for performing load operations in association with the firstset of energy storage units.
 15. A hierarchical energy managementcomputing system comprising: a resource manager configured to determinean allocation of power for a first plurality of energy storage unitsassociated with a first controller and a second plurality of energystorage units associated with a second controller, the allocation ofpower determined based on a first state-of-charge metric associated withthe first plurality of energy storage units and a second state-of-chargeassociated with the second plurality of energy storage units; a set ofcontrollers, including the first controller and the second controller,managed by the resource manager, each controller managing a set ofenergy storage units in relation to charging from and/or discharging toan electric power grid; and a set of energy storage units, each energystorage unit including an energy storage device and a power conversiondevice that interfaces with the electric power grid, wherein the firstplurality of energy storage units is managed by the first controller andthe second plurality of energy storage units is managed by the secondcontroller.
 16. The system of claim 15, wherein the resource manager,the set of controllers, and the set of energy storage units reside at anenergy resource site corresponding with the electric power grid.
 17. Thesystem of claim 15, wherein the first portion of the set of energystorages devices are managed by the first controller and the secondportion of the set of energy storage devices are managed by the secondcontroller based on a predetermined configuration of the set of energystorage devices at an energy resource site.
 18. The system of claim 15,wherein each controller of the set of controllers communicates with theresource manager and a corresponding set of energy storage units. 19.The system of claim 15, wherein the first state-of-charge metriccomprises an average state-of-charge of the first plurality of energystorage units, and the second state-of-charge metric comprises anaverage state-of-charge of the second plurality of energy storage units.20. The system of claim 15, wherein each energy storage unit chargesand/or discharges in accordance with the power allocation correspondingwith the energy storage unit.